This guide explains how to manage token metadata in Sequence Builder with the help from Pinata for IPFS hosting.
id.json
(like 1.json
, 2.json
, etc.). These files should look something like this at a minimum:
ipfs
address for each token. To do this, simply copy the CID (Content Identifier) for each file from Pinata and paste it after ipfs://
in your JSON files. It should look like this:
setBaseMetadataURI
allows the creator to set the base metadata URL for this contract. You want this to point to the JSON files you’ve created, depending on NFT ID.mint
mints one of your tokens and sends it to an address of your choosing.setBaseMetadataURI
, expand it, and under tokenBaseURI
paste the URL for the JSON folder preview you got from Pinata earlier. It should look something like this:
.json
suffix. So if you mint token ID 123, it will look for tokenBaseURI + 123.json
.
mint
, expand it, and fill in the details:
to (address)
: This is the address that the token will be sent to. Use your Sequence wallet address or any other valid address.tokenId (uint256)
: This is your token ID. As long as you have a tokenId.json
file already uploaded to pinata.cloud under the folder, it will work.amount (uint256)
: The number of tokens to mint (usually 1).data (bytes)
: Enter 0x00
for this simple process.https://metadata.sequence.app/tokens/<chain-name>/<contract-address>/<token-id>/refresh
Now that you are ready to mint, you might want to read about how you can launch your own serverless endpoint for securely minting tokens.